Hello all,

I have installed Exchange 2013 (CAS Role) on a Windows 2008 R2 server. All the requirements where passed.

After installing and the reboot, I am unable to start the Exchange Toolbox. It gives the following error:

Unhandled Exception in Managed Code Snap-in

FX:{714FA079-DC14-470f-851C-B7EAAA4177C1}

Exception type: System.Runtime.Serialization.SerializationException

Exception stack trace:

   at Microsoft.ManagementConsole.Internal.IMessageClient.ProcessRequest(Request request)
   at Microsoft.ManagementConsole.Executive.RequestStatus.BeginRequest(IMessageClient messageClient, RequestInfo requestInfo)
   at Microsoft.ManagementConsole.Executive.SnapInRequestOperation.ProcessRequest()
   at Microsoft.ManagementConsole.Executive.Operation.OnThreadTransfer(SimpleOperationCallback callback)

Any help is appreciated and with kind regards,

Willem-Jan

Are you able to open EAC?

Hello Gulab,

Thanks for your reply. If I go to 'https://localhost/ecp' then the 'Outlook Web Apps' page is shown instead of 'Exchange Admin Center'.

So my answer is 'no'.

With kind regards,

Willem-Jan

I am sure if you log In it will take you to EAC page.
Did you tried?

Restart IIS service and try Exchange ToolBox.

Hello Gulab,

I have done a iisreset. No luck at all. If I logon to 'https://localhost/ecp' then I get an 'Outlook Web App' login screen. If I logon, then I will get a 500 Error message (Internal Server Error).

Also I have checked the eventvwr.

When I start Toolbox it generates the following error:

Faulting application name: mmc.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc808

Faulting module name: KERNELBASE.dll, version: 6.1.7601.17932, time stamp: 0x503285c2

Exception code: 0xe0434352

Fault offset: 0x000000000000caed

Faulting process id: 0x1264

Faulting application start time: 0x01cdd610260197fc

Faulting application path: C:\Windows\system32\mmc.exe

Faulting module path: C:\Windows\system32\KERNELBASE.dll

Report Id: 812f1288-4203-11e2-ba2c-00155d00f202

And also:

Performance counter updating error. Counter name is Process ID, category name is MSExchangeRemotePowershell. Optional code: 2. Exception: The exception thrown is : System.InvalidOperationException: The requested Performance Counter is not a custom counter, it has to be initialized as ReadOnly.

at System.Diagnostics.PerformanceCounter.InitializeImpl()

at System.Diagnostics.PerformanceCounter.get_RawValue()

at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.get_RawValue()

Last worker process info : System.ArgumentException: Process with an Id of 4152 is not running.

at System.Diagnostics.Process.GetProcessById(Int32 processId)

at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.GetLastWorkerProcessInfo()

Processes running while Performance counter failed to update:

800 svchost

1688 svchost

3384 svchost

260 smss

748 svchost

5064 winlogon

4672 inetinfo

344 csrss

1144 vmicsvc

964 svchost

1228 vmicsvc

1068 spoolsv

868 svchost

3804 conhost

420 winlogon

952 WMSvc

1772 rundll32

4776 sppsvc

1124 vmicsvc

1568 conhost

588 svchost

3524 w3wp

1476 MSExchangeHMHost

496 lsm

4856 mmc

2452 Microsoft.Exchange.ServiceHost

844 rdpclip

4432 csrss

3224 w3wp

4004 svchost

488 lsass

2712 svchost

664 svchost

5036 w3wp

1196 vmicsvc

1640 ctfmon

2440 cmd

392 wininit

480 services

2164 MSExchangeFrontendTransport

2256 explorer

1732 taskeng

384 csrss

1540 MSExchangeHMWorker

1004 svchost

736 LogonUI

1684 svchost

2000 msdtc

376 svchost

2332 svchost

1796 rundll32

1172 vmicsvc

1260 svchost

3876 dwm

5100 TrustedInstaller

812 Microsoft.Exchange.Directory.TopologyService

2500 Microsoft.Exchange.UM.CallRouter

1340 Microsoft.Exchange.Diagnostics.Service

4 System

2940 svchost

1604 SMSvcHost

0 Idle

Performance Counters Layout information: FileMappingNotFoundException for category MSExchangeRemotePowershell : Microsoft.Exchange.Diagnostics.FileMappingNotFoundException: Cound not open File mapping for name Global\netfxcustomperfcounters.1.0msexchangeremotepowershell. Error Details: 2

at Microsoft.Exchange.Diagnostics.FileMapping.OpenFileMapping(String name, Boolean writable)

at Microsoft.Exchange.Diagnostics.PerformanceCounterMemoryMappedFile.Initialize(String fileMappingName, Boolean writable)

at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.GetAllInstancesLayout(String categoryName)

So there is something wrong, but what?

On the server I have only installed the CAS role. The mailboxes are on a Exchange 2007 server.

Hope this helps and with kind regards,

Willem-Jan

Hello Gulab,

Thanks for your reply. If I go to 'https://localhost/ecp' then the 'Outlook Web Apps' page is shown instead of 'Exchange Admin Center'.

So my answer is 'no'.

With kind regards,

Willem-Jan

That's normal behavior. You'll see EAC after logon.

Install Exchange 2013 RTM on Windows 2008 R2

Hello Gulab,

I have done a iisreset. No luck at all. If I logon to 'https://localhost/ecp' then I get an 'Outlook Web App' login screen. If I logon, then I will get a 500 Error message (Internal Server Error).

Also I have checked the eventvwr.

When I start Toolbox it generates the following error:

Faulting application name: mmc.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc808

Faulting module name: KERNELBASE.dll, version: 6.1.7601.17932, time stamp: 0x503285c2

Exception code: 0xe0434352

Fault offset: 0x000000000000caed

Faulting process id: 0x1264

Faulting application start time: 0x01cdd610260197fc

Faulting application path: C:\Windows\system32\mmc.exe

Faulting module path: C:\Windows\system32\KERNELBASE.dll

Report Id: 812f1288-4203-11e2-ba2c-00155d00f202

And also:

Performance counter updating error. Counter name is Process ID, category name is MSExchangeRemotePowershell. Optional code: 2. Exception: The exception thrown is : System.InvalidOperationException: The requested Performance Counter is not a custom counter, it has to be initialized as ReadOnly.

at System.Diagnostics.PerformanceCounter.InitializeImpl()

at System.Diagnostics.PerformanceCounter.get_RawValue()

at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.get_RawValue()

Last worker process info : System.ArgumentException: Process with an Id of 4152 is not running.

at System.Diagnostics.Process.GetProcessById(Int32 processId)

at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.GetLastWorkerProcessInfo()

Processes running while Performance counter failed to update:

800 svchost

1688 svchost

3384 svchost

260 smss

748 svchost

5064 winlogon

4672 inetinfo

344 csrss

1144 vmicsvc

964 svchost

1228 vmicsvc

1068 spoolsv

868 svchost

3804 conhost

420 winlogon

952 WMSvc

1772 rundll32

4776 sppsvc

1124 vmicsvc

1568 conhost

588 svchost

3524 w3wp

1476 MSExchangeHMHost

496 lsm

4856 mmc

2452 Microsoft.Exchange.ServiceHost

844 rdpclip

4432 csrss

3224 w3wp

4004 svchost

488 lsass

2712 svchost

664 svchost

5036 w3wp

1196 vmicsvc

1640 ctfmon

2440 cmd

392 wininit

480 services

2164 MSExchangeFrontendTransport

2256 explorer

1732 taskeng

384 csrss

1540 MSExchangeHMWorker

1004 svchost

736 LogonUI

1684 svchost

2000 msdtc

376 svchost

2332 svchost

1796 rundll32

1172 vmicsvc

1260 svchost

3876 dwm

5100 TrustedInstaller

812 Microsoft.Exchange.Directory.TopologyService

2500 Microsoft.Exchange.UM.CallRouter

1340 Microsoft.Exchange.Diagnostics.Service

4 System

2940 svchost

1604 SMSvcHost

0 Idle

Performance Counters Layout information: FileMappingNotFoundException for category MSExchangeRemotePowershell : Microsoft.Exchange.Diagnostics.FileMappingNotFoundException: Cound not open File mapping for name Global\netfxcustomperfcounters.1.0msexchangeremotepowershell. Error Details: 2

at Microsoft.Exchange.Diagnostics.FileMapping.OpenFileMapping(String name, Boolean writable)

at Microsoft.Exchange.Diagnostics.PerformanceCounterMemoryMappedFile.Initialize(String fileMappingName, Boolean writable)

at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.GetAllInstancesLayout(String categoryName)

So there is something wrong, but what?

On the server I have only installed the CAS role. The mailboxes are on a Exchange 2007 server.

Hope this helps and with kind regards,

Willem-Jan

Do you have any service that is configured as Automatic but not Started? And do you have any app pool in IIS not started?

Hello all,

I have installed Exchange 2013 (CAS Role) on a Windows 2008 R2 server. All the requirements where passed.

And not the MBX role?

Hello,

All services that are configured as 'Automatic' have been started. Also all the App pools have been started.

with kind regards,

Willem-Jan

Hello,

No, as the mailbox role is on the Exchange 2007 server. As I understood that the integration between Exchange 2007 and Exchange 2013 is not fully accomplished yet.

With kind regards,

Willem-Jan

Hello,

I saw your blog. Good article. Unfortunately there is an error after logging on on Outlook Web Apps:

This error (HTTP 500 Internal Server Error) means that the website you are visiting had a server problem which prevented the webpage from displaying.

For more information about HTTP errors, see Help.

Any help is appreciated. What else can I do?

With kind regards,

Willem-Jan

Hello,

No, as the mailbox role is on the Exchange 2007 server. As I understood that the integration between Exchange 2007 and Exchange 2013 is not fully accomplished yet.

With kind regards,

Willem-Jan

You need the 2013 Mailbox role installed for the EAP to work.

And yes Its not supported to install Exchange 2013 into an existing 2007/2010 org right now. The rollup in  2007 that will support this is not out till next year.

• Edited by Andy DavidMVP, Moderator Sunday, December 09, 2012 10:45 PM
• Marked as answer by Simon_WuMicrosoft contingent staff, Moderator Friday, December 28, 2012 2:25 AM

Hello,

No, as the mailbox role is on the Exchange 2007 server. As I understood that the integration between Exchange 2007 and Exchange 2013 is not fully accomplished yet.

With kind regards,

Willem-Jan

You need the 2013 Mailbox role installed for the EAP to work.

And yes Its not supported to install Exchange 2013 into an existing 2007/2010 org right now. The rollup in  2007 that will support this is not out till next year.

• Edited by Andy DavidMVP, Moderator Sunday, December 09, 2012 10:45 PM
• Marked as answer by Simon_WuMicrosoft contingent staff, Moderator Friday, December 28, 2012 2:25 AM

Hello,

No, as the mailbox role is on the Exchange 2007 server. As I understood that the integration between Exchange 2007 and Exchange 2013 is not fully accomplished yet.

With kind regards,

Willem-Jan

You need the 2013 Mailbox role installed for the EAP to work.

And yes Its not supported to install Exchange 2013 into an existing 2007/2010 org right now. The rollup in  2007 that will support this is not out till next year.

• Edited by Andy DavidMVP, Moderator Sunday, December 09, 2012 10:45 PM
• Marked as answer by Simon_WuMicrosoft contingent staff, Moderator Friday, December 28, 2012 2:25 AM

Hello,

No, as the mailbox role is on the Exchange 2007 server. As I understood that the integration between Exchange 2007 and Exchange 2013 is not fully accomplished yet.

With kind regards,

Willem-Jan

You need the 2013 Mailbox role installed for the EAP to work.

And yes Its not supported to install Exchange 2013 into an existing 2007/2010 org right now. The rollup in  2007 that will support this is not out till next year.

• Edited by Andy DavidMVP, Moderator Sunday, December 09, 2012 10:45 PM
• Marked as answer by Simon_WuMicrosoft contingent staff, Moderator Friday, December 28, 2012 2:25 AM

Hello,

I saw your blog. Good article. Unfortunately there is an error after logging on on Outlook Web Apps:

This error (HTTP 500 Internal Server Error) means that the website you are visiting had a server problem which prevented the webpage from displaying.

For more information about HTTP errors, see Help.

Any help is appreciated. What else can I do?

With kind regards,

Willem-Jan

Without the mailbox role installed, Exchange 2013 isnt going to work. All the rendering is done at the mbx server. All the CAFE role does is proxy and it isnt going to proxy to the 2007 server correctly until the 2007 rollup that supports that is released. Sorry.

• Marked as answer by WillemPiloot Monday, December 10, 2012 8:20 AM

Hello,

I saw your blog. Good article. Unfortunately there is an error after logging on on Outlook Web Apps:

This error (HTTP 500 Internal Server Error) means that the website you are visiting had a server problem which prevented the webpage from displaying.

For more information about HTTP errors, see Help.

Any help is appreciated. What else can I do?

With kind regards,

Willem-Jan

Without the mailbox role installed, Exchange 2013 isnt going to work. All the rendering is done at the mbx server. All the CAFE role does is proxy and it isnt going to proxy to the 2007 server correctly until the 2007 rollup that supports that is released. Sorry.

• Marked as answer by WillemPiloot Monday, December 10, 2012 8:20 AM

Hello,

I saw your blog. Good article. Unfortunately there is an error after logging on on Outlook Web Apps:

This error (HTTP 500 Internal Server Error) means that the website you are visiting had a server problem which prevented the webpage from displaying.

For more information about HTTP errors, see Help.

Any help is appreciated. What else can I do?

With kind regards,

Willem-Jan

Without the mailbox role installed, Exchange 2013 isnt going to work. All the rendering is done at the mbx server. All the CAFE role does is proxy and it isnt going to proxy to the 2007 server correctly until the 2007 rollup that supports that is released. Sorry.

• Marked as answer by WillemPiloot Monday, December 10, 2012 8:20 AM

Hello,

I saw your blog. Good article. Unfortunately there is an error after logging on on Outlook Web Apps:

This error (HTTP 500 Internal Server Error) means that the website you are visiting had a server problem which prevented the webpage from displaying.

For more information about HTTP errors, see Help.

Any help is appreciated. What else can I do?

With kind regards,

Willem-Jan

Without the mailbox role installed, Exchange 2013 isnt going to work. All the rendering is done at the mbx server. All the CAFE role does is proxy and it isnt going to proxy to the 2007 server correctly until the 2007 rollup that supports that is released. Sorry.

• Marked as answer by WillemPiloot Monday, December 10, 2012 8:20 AM

Hello,

I saw your blog. Good article. Unfortunately there is an error after logging on on Outlook Web Apps:

This error (HTTP 500 Internal Server Error) means that the website you are visiting had a server problem which prevented the webpage from displaying.

For more information about HTTP errors, see Help.

Any help is appreciated. What else can I do?

With kind regards,

Willem-Jan

I saw you didn't install 2013 mailbox.

Unfortunatly, Exchange 2013 installation should be mailbox first, CAS follows. Or you can install both at same time. 

Hello Andy,

Thanks for your reply. Then I will wait until the rollup package is available. I have installed the MBX role but if I logon I see the message that the mailbox is not available.

Also I have marked your reply as answer.

With kind regards,

Willem-Jan

Hi @all

i have same problem, with login to ecp / eap... but i installed exchange 2013 on new environment. first day, access was successful, going directly to eap. in the evening, shutdown exchange, later shutdown DC. in the morning start DC, start Exchange (was only testenvironment).

all is native Server 2012 / Exchange 2013.

Any Idea, how to reconnect6 to exchange? also Exchange shell isn't able to connect to the exchange server, even if i'm domain, enterprise, schema  admin, an have setup exchange with this account. (the only one in this domain :-))

regards

Martin

As mentioned (but not documented anywhere). When you first install Exchange 2013, and install just the CAS role (as you are always supposed to install/upgrade first), and then try to run the exchange tools, powershell or the dumb web based management thing. Then, on my own I thought it may have had something to do with no mailbox server present. So installed it and everything started working... probably should be documented somewhere, somehow, as you cant manage anything in your environment without both a cas and mb role.

Hi, i have exactly same problem, dc1 win2012 + ex1 with exchange 2013, all worked 1 week.

now iam unable to shell, owa, or toolbox.

have you fixed it somehow ?

nk

I have the same issue. I have reported it to MS. Exchange Server is

i have same issue, have you guys have found any solution yet ?

help would be great appreciate thank you ! 

I had an issue off of a fresh Exchange 2013 install today where when I opened Exchange Toolbox, it crashed mmc.exe and if I tried to connect to Exchange Management Shell it gave me an error about WinRM and an HTTP URL that was inaccessible.  I found this MS KB and when I checked my bindings on my default web site, they were missing - once I put them back, Management Shell worked and then the MMC opened and didn't crash.  Hope this helps! 

http://support.microsoft.com/kb/2027062

 

i had the same error

i use Win serveur 2013R2 with exchange 2013 SP1

it was the wrong user...

check the right to use the toolbox for your user

by default the right is open for the user who installed exchange 

after that you have to manage in the new exchange groupp in you AD

bye

maybe you renamed the default database, please rename at original name, or move the mailbox arbitration at other database on the exchange.

maybe you renamed the default database, please rename at original name, or move the mailbox arbitration at other database on the exchange.